liboqs 0.9.0 release candidate 1 #1570
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Checklist as per https://github.com/open-quantum-safe/liboqs/wiki/Release-process:
OQS_VERSION_TEXTSOVERSION(if applicable)x86_64andaarch64release-testscriptoqs-demosDocker imagesprofilingDocker imageHere are the results of running the
noregress.shscript on our x86 Dev EC2 instance.... and our ARM Dev EC2 instance.
As expected, we're seeing significant performance changes in McEliece. On the bright side, our new optimized ARM implementation for Falcon seems to be performing well.
Please take a look at the release notes (found in RELEASE.md) and let me know if you feel that I missed mentioning anything important.
Finally, I also made a couple of slight edits to the
noregress.shscript to eliminate errors that (at least for me) prevented it from completing.